Broadcast and system information for machine type communication

ABSTRACT

Methods, systems, and devices are described for facilitating Machine Type Communication in a wireless communications system. Link budget-limited MTC devices, may be supported. An MTC physical broadcast channel may be utilized for the Machine Type Communication. The MTC physical broadcast channel may be transmitted over one or more subframes different from a regular physical broadcast channel. The payload for the MTC physical broadcast channel may be reduced. The MTC physical broadcast channel may also be utilized to indicate the presence of paging and/or to indicate a change in system information. Some embodiments utilize one or more MTC-specific system information blocks. The MTC-specific system information blocks may combine and/or simplify multiple system information blocks. The location of the MTC system information blocks may be predetermined or information about their location may be transmitted over the MTC physical broadcast channel. An enhanced paging channel may be used to indicate system information updates.

CROSS REFERENCES

The present application for patent claims priority benefit of U.S.Provisional Patent Application No. 61/752,339, entitled “Methods,Systems, and Devices for Broadcast and Paging Channels for Machine TypeCommunication,” filed Jan. 14, 2013, assigned to the assignee hereof,and expressly incorporated by reference herein.

BACKGROUND

Machine-to-Machine (M2M) communication or Machine Type Communication(MTC) are terms that may be used to refer to data communicationtechnologies that allow automated devices to communicate with oneanother without human intervention. For example, M2M and/or MTC mayrefer to communications from devices that integrate sensors or meters tomeasure or capture information, and relay that information to a centralserver or application. A device used in this context may be referred toas an M2M device, MTC device, and/or an MTC user equipment (UE).

MTC devices may be used in a number of different applications to, forexample, collect information or enable automated behavior of machines.Examples of applications for MTC devices include smart metering,inventory monitoring, water level monitoring, equipment monitoring,healthcare monitoring, wildlife monitoring, weather and geological eventmonitoring, fleet management and tracking, remote security sensing,physical access control, and transaction-based business charging. Themarket for MTC devices is expected to grow rapidly as industries such asautomotive, security, healthcare, and fleet management employ MTC toincrease productivity, manage costs, and/or expand customer services.

MTC devices may use a variety of wired and/or wireless communicationtechnologies. For example, MTC devices may communicate with a networkover various wireless cellular technologies and/or various wirelessnetworking technologies (e.g., IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX),etc.). MTC devices may also communicate with one another using variouspeer-to-peer technologies such as Bluetooth, ZigBee, and/or other ad-hocor mesh network technologies. The expansion of multiple access wirelessnetworks around the world has made it far easier for MTC communicationto take place and has lessened the amount of power and time necessaryfor information to be communicated between machines. These networks alsoallow an array of new business opportunities and connections betweenconsumers and producers in terms of the products being sold.

In some cases, MTC devices may be deployed in locations that makewireless communication difficult, such as in basements. There may be aneed for coverage enhancements in some cases. Transmission time interval(TTI) bundling has been employed to achieve some coverage enhancement.However, broadcast channels, such as physical broadcast channels andsystem information transmissions, may also need coverage enhancement.Additionally, much of the system information that is generallytransmitted over broadcast channels may not be needed for MTCoperations. It therefore may be beneficial to provide an MTC physicalbroadcast channel and/or MTC-specific system information blocks thatallow MTC devices to limit the amount of unnecessary informationreceived. It may also be beneficial to increase the efficiency withwhich MTC devices anticipate and decode transmissions to identifychanges in system information, and to determine whether to decodecertain system information.

SUMMARY

The described features generally relate to one or more systems, methods,and devices for facilitating Machine Type Communication in a wirelesscommunications system. For example, the techniques may be utilized tosupport link budget-limited MTC devices, such as those located inbasements. In some embodiments, an MTC physical broadcast channel may beutilized to facilitate the Machine Type Communication. The MTC physicalbroadcast channel may be transmitted over one or more subframesdifferent from a regular (e.g., legacy) physical broadcast channel. Thepayload for the MTC physical broadcast channel may be reduced, withrespect to a legacy physical broadcast channel, in some cases. The MTCphysical broadcast channel may also be utilized to indicate the presenceof paging and/or to indicate a change in system information.

In some embodiments, a method for facilitating Machine TypeCommunication in a wireless communications system includes receiving oneor more MTC-specific system information blocks at an MTC device andprocessing the one or more MTC-specific system information blocks at theMTC device.

In some embodiments, an apparatus for facilitating Machine TypeCommunication in a wireless communications system includes means forreceiving one or more MTC-specific system information blocks at theapparatus and means for processing the one or more MTC-specific systeminformation blocks at the apparatus.

In some embodiments, an apparatus for facilitating Machine TypeCommunication in a wireless communications system includes a processor,memory in electronic communication with the processor, and instructionsstored in the memory. The instructions may be executable by theprocessor to receive one or more MTC-specific system information blocksat the apparatus, and process the one or more MTC-specific systeminformation blocks.

In some embodiments, a computer program product for facilitating MachineType Communication in a wireless communications system includes anon-transitory computer readable medium storing instructions executableby a processor to receive one or more MTC-specific system informationblocks at an MTC device, and process the one or more MTC-specific systeminformation blocks at the MTC device.

In certain examples of the methods, apparatuses, and/or computer programproducts, the MTC-specific system information blocks may include acombination of system information included in two or more other systeminformation blocks.

In certain examples of the methods, apparatuses, and/or computer programproducts, the MTC-specific system information blocks may consist of asubset of system information included in one other system informationblock.

In certain examples of the methods, apparatuses, and/or computer programproducts, the other system information block or blocks may includesystem information block 1 (SIB1), system information block 2 (SIB2),and/or system information block 12 (SIB12).

In certain examples of the methods, apparatuses, and/or computer programproducts, one or more of the MTC-specific system information blocks mayinclude fields for: cell access information, scheduling information forother system information blocks, radio resource configurationinformation, MTC random access channel (RACH) configuration information,MTC paging channel configuration information, physical uplink sharedchannel (PUSCH) configuration information, power control, a timer, radioresource configuration information other than PUSCH configurationinformation, and/or sounding reference signal (SRS) configurationinformation.

In certain examples of the methods, apparatuses, and/or computer programproducts, one or more MTC-specific system information blocks may belocated at one or more predetermined locations. The one or morepredetermined locations may be a function of a cell ID, a cyclic prefixlength, and a division duplex configuration.

In certain examples, the methods, apparatuses, and/or computer programproducts may include steps for, means for, and/or instructionsexecutable by a processor for receiving information regarding one ormore locations of the MTC-specific system information blocks over an MTCphysical broadcast channel.

In certain examples, the methods, apparatuses, and/or computer programproducts may include steps for, means for, and/or instructionsexecutable by a processor for determining a sleep time of the MTC deviceexceeds a time duration, and reading one of the MTC-specific systeminformation blocks when the determined sleep time exceeds the timeduration.

Further scope of the applicability of the described methods andapparatuses will become apparent from the following detaileddescription, claims, and drawings. The detailed description and specificexamples are given by way of illustration only, since various changesand modifications within the spirit and scope of the description willbecome apparent to those skilled in the art.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentinvention may be realized by reference to the following drawings. In theappended figures, similar components or features may have the samereference label. Further, various components of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 shows a block diagram of a wireless communications system inaccordance with various embodiments;

FIG. 2A illustrates an example of a wireless communication systemincluding a radio access network or core network implementing a MachineType Communication service in accordance with various embodiments;

FIG. 2B illustrates an example of a wireless communications systemimplementing a Machine Type Communication service over an LTE/LTE-Anetwork in accordance with various embodiments;

FIG. 3 shows a block diagram of a device configured for facilitatingMachine Type Communication in a wireless communications system inaccordance with various embodiments;

FIG. 4 shows a block diagram of a device configured for facilitatingMachine Type Communication in a wireless communications system inaccordance with various embodiments;

FIG. 5 shows a block diagram of a wireless communications systemconfigured for facilitating Machine Type Communication in accordancewith various embodiments;

FIG. 6 shows a block diagram of a wireless communications systemconfigured for facilitating Machine Type Communication in accordancewith various embodiments;

FIG. 7 shows a block diagram of a wireless communications systemconfigured for facilitating Machine Type Communication in accordancewith various embodiments;

FIG. 8 shows a block diagram of a communications system configured forfacilitate Machine Type Communication in accordance with variousembodiments;

FIG. 9 shows a block diagram of an MTC device configured forfacilitating Machine Type Communication in accordance with variousembodiments;

FIG. 10 is a block diagram of a system including a base station and anMTC device in accordance with various embodiments;

FIG. 11A is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 11B is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 12A is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 12B is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 13 is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 14A is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 14B is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 15A is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 15B is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments;

FIG. 16 is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments; and

FIG. 17 is a flow chart illustrating an example of a method forfacilitating Machine Type Communication in a wireless communicationssystem in accordance with various embodiments.

DETAILED DESCRIPTION

Systems, methods, and devices are described for facilitating MachineType Communication in a wireless communications system. For example, thesystems, methods, and/or devices may support link budget limited MTCdevices, such as those MTC devices. In some embodiments, an MTC physicalbroadcast channel may be utilized to facilitate the Machine TypeCommunication. The MTC physical broadcast channel may be transmittedover one or more subframes different from a regular physical broadcastchannel. The payload for the MTC physical broadcast channel may bereduced, as compared to a legacy physical broadcast channel, in somecases. The MTC physical broadcast channel may also be utilized toindicate the presence of paging and/or to indicate a change in systeminformation.

Some embodiments utilize one or more MTC-specific system informationblocks. The MTC system information blocks may combine and simplifymultiple system information blocks. The location of the MTC-specificsystem information blocks may be predetermined or information abouttheir location may be transmitted over the MTC physical broadcastchannel. Some embodiments may also provide an enhanced paging channelthat may indicate system information updates.

Some embodiments may utilize broadcast channel designs that apply to newcarrier types (NCT). For example, physical broadcast channels (PBCH)and/or system information blocks (SIB) may be designed differently fromlegacy carrier types in accordance with various embodiments.Furthermore, for tools and techniques that may apply to NCT, someembodiments may utilize signaling of PDCCH and/or ePDCCH configurationsin PBCH.

Techniques described herein may be used for various wirelesscommunications systems such as cellular wireless systems, Peer-to-Peerwireless communications, wireless local access networks (WLANs), ad hocnetworks, satellite communications systems, and other systems. The terms“system” and “network” are often used interchangeably. These wirelesscommunications systems may employ a variety of radio technologies suchas Code Division Multiple Access (CDMA), Time Division Multiple Access(TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA(OFDMA), Single-Carrier FDMA (SC-FDMA), and/or other radio technologies.Examples of CDMA systems include CDMA2000, Universal Terrestrial RadioAccess (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-856standards. IS-2000 Releases 0 and A are commonly referred to as CDMA20001×, 1×, etc. IS-856 (TIA-856) is commonly referred to as CDMA20001×EV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA(WCDMA) and other variants of CDMA. Examples of TDMA systems includevarious implementations of Global System for Mobile Communications(GSM). Examples of OFDMA and OFDM systems include Ultra Mobile Broadband(UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX),IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of UniversalMobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE)and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA,E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from anorganization named “3rd Generation Partnership Project” (3GPP). CDMA2000and UMB are described in documents from an organization named “3rdGeneration Partnership Project 2” (3GPP2). The techniques describedherein may be used for the systems and radio technologies mentionedabove as well as other systems and radio technologies.

Thus, the following description provides examples, and is not limitingof the scope, applicability, or configuration set forth in the claims.Changes may be made in the function and arrangement of elementsdiscussed without departing from the spirit and scope of the disclosure.Various embodiments may omit, substitute, or add various procedures orcomponents as appropriate. For instance, the methods described may beperformed in an order different from that described, and various stepsmay be added, omitted, or combined. Also, features described withrespect to certain embodiments may be combined in other embodiments.

Referring first to FIG. 1, a block diagram illustrates an example of awireless communications system 100 in accordance with variousembodiments. The system 100 includes base stations 105 (or cells),communication devices 115, a base station controller 120, and a corenetwork 130 (the controller 120 may be integrated into the core network130). The system 100 may support operation on multiple carriers(waveform signals of different frequencies). Multi-carrier transmitterscan transmit modulated signals simultaneously on the multiple carriers.For example, each modulated signal may be a multi-carrier channelmodulated according to the various radio technologies described above.Each modulated signal may be sent on a different carrier and may carrycontrol information (e.g., pilot signals, control channels, etc.),overhead information, data, etc. The system 100 may be a multi-carrierLTE/LTE-A network capable of efficiently allocating network resources.

The base stations 105 may wirelessly communicate with the devices 115via a base station antenna (not shown). The base stations 105 maycommunicate with the devices 115 under the control of the base stationcontroller 120 via multiple carriers. Each of the base station 105 sitesmay provide communication coverage for a respective geographic area. Insome embodiments, base stations 105 may be referred to as a basetransceiver station, a radio base station, a radio transceiver, a basicservice set (BSS), an extended service set (ESS), a NodeB, eNodeB (eNB),Home NodeB, a Home eNodeB, or some other suitable terminology. Thecoverage area for each base station 105 here is identified as 110-a,110-b, or 110-c. The coverage area for a base station may be dividedinto sectors (not shown, but making up only a portion of the coveragearea). The system 100 may include base stations 105 of different types(e.g., macro, pico, and/or femto base stations). A macro base stationmay provide communication coverage for a relatively large geographicarea (e.g., 35 km in radius). A pico base station may provide coveragefor a relatively small geographic area (e.g., 12 km in radius), and afemto base station may provide communication coverage for a relativelysmaller geographic area (e.g., 5 km in radius). There may be overlappingcoverage areas for different technologies.

The devices 115 may be dispersed throughout the coverage areas 110. Eachdevice 115 may be stationary or mobile. In one configuration, thedevices 115 may be able to communicate with different types of basestations such as, but not limited to, macro base stations, pico basestations, and femto base stations.

Some of the devices 115 may be Machine Type Communication (MTC) devices115 that perform various functions, capture information, and/orcommunicate information with limited or no human intervention. Forexample, MTC devices 115 may include sensors and/or meters formonitoring and/or tracking other devices, environmental conditions, etc.MTC devices 115 may be standalone devices or, in embodiments, MTCdevices 115 may be incorporated in other devices. For example, devicessuch as cellular phones and wireless communications devices, personaldigital assistants (PDAs), other handheld devices, netbooks, notebookcomputers, surveillance cameras, handled medical scanning devices, homeappliances, etc. may include one or more MTC devices 115. In the ensuingdescription, various techniques are described as applied tocommunications and processing for a system including a network and oneor more MTC devices. It should be understood that the describedtechniques may be advantageously applied to other devices such as thoseincorporating MTC devices and/or other wireless communication devices.

The information collected by the MTC devices 115 may be transmittedacross a network that includes components of system 100 to a back-endsystem, such as a server. The transmission of data to/from the MTCdevices 115 may be routed through the base stations 105. The basestations 105 may communicate with the MTC devices 115 on a forward linkfor transmitting signaling and/or information to the MTC devices 115 anda reverse link for receiving signaling and/or information from the MTCdevices 115.

In one example, the network controller 120 may be coupled to a set ofbase stations and provide coordination and control for these basestations 105. The controller 120 may communicate with the base stations105 via a backhaul (e.g., core network 130). The base stations 105 mayalso communicate with one another directly or indirectly and/or viawireless or wireline backhaul.

The different aspects of system 100, such as the MTC devices 115, thebase stations 105, the core network 130, and/or the controller 120 maybe configured to utilize one or more MTC physical broadcast channels.For example, the base stations 105, the core network 130, and/or thecontroller 120 may configure information to transmit over an MTCphysical broadcast channel. The information may be transmitted over theMTC physical broadcast channel to MTC devices 115. The MTC devices 115may be configured to receive information transmitted over an MTCphysical broadcast channel. The information received over the MTCphysical broadcast channel may be processed by the MTC devices 115.

The different aspects of system 100, such the MTC devices 115, the basestations 105, the core network 130, and/or the controller 120 may beconfigured to transmit and/or receive information that include a reducedpayload for the MTC physical broadcast channel with respect to a regularphysical broadcast channel. The information transmitted and/or receivedover the MTC physical broadcast channel may include receiving a pagingindicator transmitted over the MTC physical broadcast channel. Someembodiments include transmitting and/or receiving a system informationchange indicator transmitted over the MTC physical broadcast channelutilizing different aspects of system 100, such the MTC devices 115, thebase stations 105, the core network 130, and/or the controller 120.

In some embodiments, the system 100 is an LTE/LTE-A network. Asdescribed below, LTE/LTE-A defines numerous different system informationblocks (SIBs) for conveying system information from eNBs 105 to UEs 115.Within this description, SIBs presently defined in LTE/LTE-A may bereferred to as “regular system information blocks” or “other systeminformation blocks” to distinguish them from MTC-specific systeminformation blocks.

In some embodiments, the different aspects of system 100, such as thebase stations 105, the core network 130, and/or the controller 120 mayconfigure one or more MTC-specific system information blocks. The one ormore MTC-specific system information blocks may be transmitted to andreceived by the MTC devices 115 where the one or more MTC-specificsystem information blocks may be processed. The MTC-specific systeminformation blocks may include at least a portion from each of multipleregular system information blocks combined into at least one of the oneor more MTC-specific system information blocks. In some cases, the oneor more MTC-specific system information blocks may be located at one ormore predetermined locations. The one or more predetermined locationsmay be a function of at least a cell ID, a cyclic prefix length, adivision duplex configuration. The different aspects of system 100, suchas the MTC devices 115, the base stations 105, the core network 130,and/or the controller 120 may be configured to transmit and/or receiveinformation regarding one or more locations of the one or moreMTC-specific system information blocks over an MTC physical broadcastchannel.

In some embodiments, the different aspects of system 100, such the basestations 105, the core network 130, and/or the controller 120 mayconfigure one or more MTC-specific system information blocks. A countermay be configured and/or transmitted over a paging channel to the MTCdevices 115 to indicate a system information configuration or a changein the system information configuration. The counter may includemultiple bits to reflect the system information configuration or thechange in the system information. The MTC devices 115 may be configuredto determine the system information configuration or a change in thesystem information configuration by utilizing the counter received overthe paging channel.

In some embodiments, the MTC devices 115 may be configured to determinewhether a sleep time of the MTC device 115 exceeds a time duration. AnMTC-specific system information block may be read by the MTC devices 115when the determined sleep time exceeds the time duration.

FIG. 2A illustrates an example of a wireless communication system 200-aincluding a Radio Access Network (RAN) or Core Network 130-aimplementing a machine type communication service in accordance withvarious embodiments. The system 200-a may include a number of MTCdevices 115-a and an MTC server 210. Communications between the server210 and MTC devices 115 may be routed through a base station 105 thatmay be considered part of the Core Network/RAN 130-a, which may be anexample of the core network 130 of FIG. 1. The base station 105-a may bean example of the base stations illustrated in FIG. 1. The MTC devices115-a may be examples of the MTC devices 115 illustrated in FIG. 1. Oneskilled in the art would understand that the quantity of MTC devices115-a, Core Networks/RANs 130-a, and MTC servers 210 shown in FIG. 2 isfor illustration purposes only and should not be construed as limiting.

The wireless communication system 200-a may be operable to facilitateMachine Type Communication between one or more MTC devices 115-a and/orone or more base stations 105-a. Machine Type Communication may includecommunications between one or more devices without human intervention.In one example, Machine Type Communication may include the automatedexchange of data between a remote machine, such as an MTC device 115-a,and a back-end IT infrastructure, such as the MTC server 210, withoutuser intervention. The transfer of data from an MTC device 115-a to theMTC server 210 via the Core Network/RAN 130-a (e.g., via the basestation 105-a) may be performed using reverse link communications. Datacollected by the MTC devices 115-a (e.g., monitoring data, sensor data,meter data, etc.) may be transferred to the MTC server 210 on thereverse link communications.

The transfer of data from the MTC server 210 to an MTC device 115-a viathe base station 105-a may be performed via forward link communications.The forward link may be used to send instructions, software updates,and/or messages to the MTC devices 115-a. The instructions may instructthe MTC devices 115-a to remotely monitor equipment, environmentalconditions, etc. Machine Type Communication may be used with variousapplications such as, but not limited to, utility metering, remotemonitoring, measurement and condition recording, fleet management andasset tracking, in-field data collection, distribution, physical accesscontrol, and/or storage, etc. The base station 105-a may generate one ormore forward link frames with a small number of channels to transmitinstructions, software updates, and/or messages. The various MTC devices115-a may wake up to monitor a specific frame when instructions or otherdata is included on a channel of that frame.

In some embodiments, the different aspects of system 200-a, such as theMTC devices 115-a and/or Core Networks/RANs 130-a may be configured toutilize one or more MTC physical broadcast channels. For example, theCore Networks/RANs 130-a may configure information to transmit over anMTC physical broadcast channel. The information may be transmitted overthe MTC physical broadcast channel to MTC devices 115-a. The MTC devices115-a may be configured to receive information transmitted over an MTCphysical broadcast channel. The information received over the MTCphysical broadcast channel may be processed by the MTC devices 115-a.

The different aspects of system 200-a, such the MTC devices 115-a and/orCore Networks/RANs 130-a may be configured to transmit and/or receiveinformation that include a reduced payload for the MTC physicalbroadcast channel, where the payload is reduced with respect to aregular physical broadcast channel. The information transmitted and/orreceived over the MTC physical broadcast channel may include receiving apaging indicator transmitted over the MTC physical broadcast channel.Some embodiments include transmitting and/or receiving a systeminformation change indicator transmitted over the MTC physical broadcastchannel utilizing different aspects of system 200-a, such as the MTCdevices 115-a and/or Core Networks/RANs 130-a.

In some embodiments, the different aspects of system 200-a, such as CoreNetworks/RANs 130-a configure one or more MTC-specific systeminformation blocks. The one or more MTC-specific system informationblocks may be transmitted to and received by the MTC devices 115 wherethe one or more MTC-specific system information blocks may be processed.The MTC-specific system information blocks may include at least aportion from each of several other system information blocks combinedinto at least one or more MTC-specific system information blocks.

In some cases, the MTC-specific system information blocks may be locatedat one or more predetermined locations. The predetermined locations maybe a function of at least a cell ID, a cyclic prefix length, a divisionduplex configuration. The different aspects of system 200-a, such as MTCdevices 115-a and/or Core Networks/RANs 130-a may be configured totransmit and/or receive information regarding one or more locations ofthe one or more MTC-specific system information blocks over an MTCphysical broadcast channel.

In some embodiments, the different aspects of system 200-a, such the MTCdevices 115-a and/or Core Networks/RANs 130-a may configure one or moreMTC-specific system information blocks. A counter may be configuredand/or transmitted to the MTC devices 115-a to indicate a systeminformation configuration or a change in the system informationconfiguration. The counter may include multiple bits to reflect thesystem information configuration or the change in the systeminformation. The MTC devices 115-a may be configured to determine thesystem information configuration or a change in the system informationconfiguration by utilizing the counter. The MTC devices 115-a mayreceive the counter over any one of several channels, including a pagingchannel, a PBCH, or an MTC physical broadcast channel.

In some embodiments, the MTC devices 115-a may be configured todetermine whether a sleep time of the MTC device 115-a exceeds a timeduration. A system information block (e.g., an MTC-specific systeminformation block) may be read by the MTC devices 115-a when thedetermined sleep time exceeds the time duration.

FIG. 2B illustrates an example of a wireless communications system 200-bimplementing a machine type communication service over an LTE/LTE-Anetwork in accordance with various embodiments. System 200-b may be anexample of system 200-a of FIG. 2A and/or system 100 of FIG. 1. TheLTE/LTE-A network may include Evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN) 205 and Evolved Packet Core (EPC) 220. The LTE E-UTRAN205 and EPC 220 may be configured for supporting end-to-endpacket-switched communications. EPC 220 may include a Packet DataNetwork (PDN) Gateway 222. The PDN Gateway 222 may be connected to oneor more Internet Protocol (IP) Networks 230. IP Networks 230 may includeOperator IP Networks as well as external IP Networks. For example, IPNetworks 230 may include the Internet, one or more Intranets, an IPMultimedia Subsystem (IMS), and a PS Streaming Service (PSS). The PDNGateway 222 may provide UE IP address allocation as well as otherfunctions. The EPC 220 may interconnect with other access networks. Forexample, EPC 220 may interconnect with UTRAN 242 and/or GERAN 244 viaone or more Serving GPRS Support Nodes (SGSNs) 240.

EPC 220 may include one or more Serving Gateways 224 and/or MobilityManagement Entities (MME) 226. The Serving Gateway 224 may handle theinterface to E-UTRAN 205 and provide a communication point for inter-RATmobility (e.g., handover to UTRAN 242 and/or GERAN 244, etc.).Generally, the MME 226 may provide bearer and connection managementwhile the Serving Gateway 224 may transfer user IP packets between eNBs105 and other network end-points (e.g., PDN GW 222, etc.). For example,MME 226 may manage intra-RAT mobility functions (e.g., Serving Gatewayselection) and/or UE tracking management. The Serving Gateway 224 andthe MME 226 may be implemented in one physical node of EPC 220 or inseparate physical nodes. A Home Subscriber Service (HSS) and/or homelocation register (HLR) node 260 may provide service authorizationand/or user authentication for UEs. HSS/HLR node 260 may be incommunication with one or more databases 262. Such service authorizationand/or user authentication information may include network subscriptionauthorization for UICCs or SIM cards associated with a number of MTCdevices.

E-UTRAN 205 may include one or more base stations or eNBs 105-b, whichprovide user and control plane protocol terminations for UEs (e.g., MTCdevices 115) over the air interface of the LTE network. The eNBs 105-bmay be connected with an X2 interface for intra-eNB communication. TheeNBs 105-b may be connected to Serving Gateway 224 and/or MME 226 overan S-1 interface 215 for communicating data traffic and/or control planeinformation. The MTC devices 115-b may be configured to collaborativelycommunicate with multiple eNBs 105 through, for example, Multiple InputMultiple Output (MIMO), Coordinate Multi-Point (CoMP), or other schemesas described in more detail below.

In embodiments, wireless communications network 200-b includes an MTCinter-working function (IWF) 250, which may provide an interface betweenEPC 220 and one or more external MTC Servers 210 for providing MTCservice within the LTE network. MTC IWF 250 may be implemented in one ormore existing physical nodes of the EPC 220 (e.g., Serving Gateway 224,etc.), or in a separate physical node connected to EPC 220.

The communication networks that may accommodate some of the variousdisclosed embodiments may be packet-based networks that operateaccording to a layered protocol stack. In the user plane, communicationsat the bearer or Packet Data Convergence Protocol (PDCP) layer may beIP-based. A Radio Link Control (RLC) layer may perform packetsegmentation and reassembly to communicate over logical channels. AMedium Access Control (MAC) layer may perform priority handling andmultiplexing of logical channels into transport channels. The MAC layermay also use hybrid automatic repeat request (HARM) techniques toprovide retransmission at the MAC layer to ensure reliable datatransmission. In the control plane, the Radio Resource Control (RRC)protocol layer may provide establishment, configuration, and maintenanceof an RRC connection between the UE and the network used for the userplane data. At the Physical layer, the transport channels may be mappedto Physical channels

In order to access and operate properly with an eNB 105, an MTC device115 may need to acquire system information. System information mayinclude information related to: uplink/downlink configuration, uplinkand downlink bandwidth, random-access transmissions, uplink powercontrol, and the like. In LTE/LTE-A networks, system information isconveyed in a master information block (MIB) and several systeminformation blocks (SIBs). Generally, the MIB, which may be transmittedutilizing a broadcast channel (BCH), includes a limited amount of systeminformation, while the various SIBs, which may be transmitted utilizinga downlink shared channel (DL-SCH), include the bulk of the necessarysystem information. Such may be the case in the systems 100 and 200 ofFIG. 1, FIG. 2A, and FIG. 2B.

LTE/LTE-A defines different SIBs according to the type of systeminformation that each SIB conveys. SIB1 includes cell accessinformation, including cell identity information, and it may indicatewhether a UE is allowed to camp on an eNB 105. SIB1 also includes cellselection information (or cell selection parameters). Additionally, SIB1includes scheduling information for other SIBs. SIB2 includes cellaccess information and parameters related to common and shared channels,including radio resource configuration information. SIB3 includes cellreselection parameters. SIB4 and SIB5 include reselection informationabout neighboring LTE cells. SIB6 through SIB8 include reselectioninformation about non-LTE (e.g., UMTS, GERAN, and CDMA2000) neighboringcells. SIB9 includes the name of a Home eNB. SIB10 through SIB12 includeemergency notification information (e.g., tsunami and earthquakewarnings), which may be of relevant to MTC devices. And SIB13 includesinformation related to multimedia broadcast/multicast service (MBMS)configuration.

The eNBs 105 of the systems 100 and 200 of FIGS. 1, 2A, and 2B may alsobe capable of configuring MTC-specific system information blocks, whichthe MTC devices 115 are configured to receive and process. For instance,an MTC-specific system information block may include a combination ofother system information blocks, or a combination of system informationincluded in two or more other system information blocks. In someembodiments, an MTC-specific system information block includes SIB1,SIB2, and/or SIB 12. In some cases, an MTC-specific system informationblock includes fields for cell access information, schedulinginformation for other SIB, and radio resource configuration information.

Additionally or alternatively, an MTC-specific system information blockmay consist of a subset of system information included in one othersystem information block—this may include system information relevant toan MTC and exclude extraneous system information. For example, anMTC-specific system information block may include a subset of systeminformation available in SIB1, SIB2, or SIB12. For example, anMTC-specific system information block may include fields for cell accessinformation and cell selection, or it may include fields for schedulinginformation for other system information blocks.

In some cases, the MTC-specific system information blocks includesMTC-specific channel configuration information—e.g., configurationinformation for an MTC random access channel (RACH) or an MTC pagingchannel. An MTC-specific system information block may also includeconfiguration information for a physical uplink shared channel (PUSCH),power control, and/or a timer. While in other embodiments, anMTC-specific system information block may include fields for radioresource configuration information other than PUSCH and soundingreference signal (SRS) configuration information.

The different aspects of system 200-b may implement differentembodiments as discussed above with respect to systems 200-a of FIG. 2and/or system 100 of FIG. 1. Further details regarding differentembodiments are also provided below with respect to device 300 of FIG. 3and/or device 400 of FIG. 4. Some specific embodiments are also providedwith respect to systems 500 of FIG. 5, system 600 of FIG. 6, and/orsystem 700 of FIG. 7, which may be implemented utilizing systems such assystem 200-b of FIG. 2B.

Turning next to FIG. 3, a block diagram illustrates a device 300configured for facilitating Machine Type Communication (MTC) in awireless communications system in accordance with various embodiments.The device 300 may be an example of one or more aspects of the basestations 105 as shown in FIG. 1, FIG. 2A, and/or FIG. 2B. The device 300may also be a processor. The device 300 may include receiver 310, MTCinformation configuration module 320, and/or transmitter 330. Each ofthese components may be in communication with each other. In some cases,these components may be integrated with each other; for example, MTCinformation configuration module 320 may be integrated transmitter 330.

These components of the device 300 may, individually or collectively, beimplemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors. Each of the noted modules may be ameans for performing one or more functions related to operation of thedevice 300.

MTC information configuration module 320 and/or transmitter 330 mayconfigure information to transmit over an MTC physical broadcastchannel. The information may be transmitted over the MTC physicalbroadcast channel through transmitter 330. In some cases, theinformation may be transmitted to multiple MTC devices.

In some embodiments, an MTC physical broadcast channel is transmittedwithin a subframe separate from a regular physical broadcast channel.The MTC physical broadcast channel may be transmitted within a fifthsubframe (SF5) of a frame, within the center six resource blocks (RBs).In some cases, the information is transmitted multiple times within aframe.

MTC information configuration module 320 and/or transmitter 330 mayconfigure the information to transmit over the MTC physical broadcastchannel to include reducing a payload for the MTC physical broadcastchannel with respect to a regular physical broadcast channel. Reducingthe payload for the MTC physical broadcast channel may include removingone or more bits utilized to reflect a downlink bandwidth, a systemframe number, a physical hybrid ARQ indicator channel (PHICH) duration,a PHICH group, one or more reserved bits, or a cyclic redundancy checkwith respect to the regular physical broadcast channel.

MTC information configuration module 320 and/or transmitter 330 may beconfigured to indicate an MTC-specific system information block locationover the MTC physical broadcast channel. MTC information configurationmodule 320 and/or transmitter 330 may be configured to transmit an MTCsystem frame number over the MTC physical broadcast channel. The MTCsystem frame number may, for instance, map to a longer frame length thana regular system frame number.

Configuring the information to transmit over the MTC physical broadcastchannel through MTC information configuration module 320 and/ortransmitter 330 may include configuring a paging indicator to transmitover the MTC physical broadcast channel. The paging indicator mayinclude an individual bit to indicate whether there is paging for atleast one MTC device. The paging indicator may include multiple bits toindicate whether there is paging for multiple different paging groups inother cases. Configuring the information to transmit over the MTCphysical broadcast channel may include configuring a system informationchange indicator to transmit over the MTC physical broadcast channel.For example, a counter may be configured and transmitted; and thecounter may indicate a system information configuration or a change inthe system information configuration. The counter may also notify MTCdevices 115 to wake up, receive, and decode one or more MTC-specificsystem information blocks.

In some embodiments, MTC information configuration module 320 and/ortransmitter 330 may configure one or more MTC-specific systeminformation blocks. MTC information configuration module 320 and/ortransmitter 330 may transmit the one or more MTC-specific systeminformation blocks to multiple MTC devices.

Configuring the one or more MTC-specific system information blocksthrough MTC information configuration module 320 and/or transmitter 330may include combining a portion from each of multiple other systeminformation blocks into at least one of the one or more MTC-specificsystem information blocks. This may include removing portions from atleast one of the multiple regular system information blocks. The MTCinformation configuration module 320 may also configure MTC-specificsystem information blocks that include a subset of MTC-relevant, orMTC-specific information available in other system information blocks.

MTC information configuration module 320 and/or transmitter 330 may beconfigured to utilize one or more MTC fields as part of the one or moreMTC-specific system information blocks to replace one or more regularfields from one or more of the multiple system information blocks.

In some cases, the one or more MTC-specific system information blocksare located at one or more predetermined locations. The one or morepredetermined locations may be a function of at least a cell ID, acyclic prefix length, or a division duplex configuration. Someembodiments include utilizing an MTC physical broadcast channel toconvey information regarding one or more locations of the MTC-specificsystem information blocks.

In some embodiments, MTC information configuration module 320 and/ortransmitter 330 may determine a system information configuration frommultiple system information configurations. A counter may be configuredand/or transmitted through MTC information configuration module 320and/or transmitter 330 to be transmitted over a paging channel toindicate at least the determined system information configuration or achange in the determined system information configuration. The countermay include multiple bits to reflect the determined system informationconfiguration or the change in the determined system information, orboth.

Turning next to FIG. 4, a block diagram illustrates a device 400configured for facilitating Machine Type Communication in a wirelesscommunications system in accordance with various embodiments. The device400 may be an example of one or more aspects of MTC devices 115described with reference to FIGS. 1, 2A, and/or 2B, for example. Thedevice 400 may also be a processor. The device 400 may include receiver410, MTC information processing module 420, and/or transmitter 430. Eachof these components may be in communication with each other. In somecases, these components may be integrated with each other; for example,MTC information processing module 420 may be integrated with receiver410.

These components of the device 400 may, individually or collectively, beimplemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors. Each of the noted modules may be ameans for performing one or more functions related to operation of thedevice 400.

In some embodiments, MTC information processing module 420 and/orreceiver 410 may be configured to receive information transmitted overan MTC physical broadcast channel. The information received over the MTCphysical broadcast channel may be processed by MTC informationprocessing module 420 and/or receiver 410.

In some cases, the information transmitted over the MTC physicalbroadcast channel is received within a subframe separate from a legacyphysical broadcast channel. The information transmitted over the MTCphysical broadcast channel may be received within at least a fifthsubframe (SF5) of a frame rather than subframe zero (SF0), for example.The information transmitted over the MTC physical broadcast channel maybe received within the center six resource blocks (RB) of the subframe.In some cases, the information may be received multiple times within aframe.

The information may include a reduced payload for the MTC physicalbroadcast channel with respect to a regular physical broadcast channel.The reduced payload for the MTC physical broadcast channel may include areduced number of one or more bits utilized to reflect a downlinkbandwidth, a system frame number, a PHICH duration, a PHICH group, oneor more reserved bits, or a cyclic redundancy check.

MTC information processing module 420 and/or receiver 410 may beconfigured to receive an MTC-specific system information block locationover the MTC physical broadcast channel. MTC information processingmodule 420 and/or receiver 410 may be configured to receive an MTCsystem frame number over the MTC physical broadcast channel. The MTCsystem frame number may map to a longer frame length than a regularsystem frame number.

Receiving the information transmitted over the MTC physical broadcastchannel at MTC information processing module 420 and/or receiver 410 mayinclude receiving a paging indicator to transmit over the MTC physicalbroadcast channel. The paging indicator may include an individual bit toindicate whether there is paging for at least one MTC device in somecases. The paging indicator may include multiple bits to indicatewhether there is paging for a plurality of different paging groups.Receiving the information transmitted over the MTC physical broadcastchannel may include receiving a system information change indicatortransmitted over the MTC physical broadcast channel.

In some embodiments, MTC information processing module 420 and/orreceiver 410 are configured to receive one or more MTC-specific systeminformation blocks. The one or more MTC-specific system informationblocks may be processed at MTC information processing module 420 and/orreceiver 410.

Receiving the one or more MTC-specific system information blocks at MTCinformation processing module 420 and/or receiver 410 may includereceiving an MTC-specific system information block that includes aportion of system information from each of several other systeminformation blocks combined into at least one MTC-specific systeminformation blocks. MTC information processing module 420 and/orreceiver 410 may be configured to receive one or more MTC-relevantfields as part of the one or more MTC-specific system informationblocks, which may obviate the need to receive and decode one or morefields from other system information blocks.

In some cases, the one or more MTC-specific system information blocksmay be located at a predetermined location. The predetermined locationmay be a function of at least a cell ID, a cyclic prefix length, adivision duplex configuration. MTC information processing module 420and/or receiver 410 may be configured to receive information regardingone or more locations of the one or more MTC-specific system informationblocks over an MTC physical broadcast channel.

In some embodiments, MTC information processing module 420 and/orreceiver 410 may be configured to receive a counter to indicate a systeminformation configuration or a change in the system informationconfiguration. The counter may include multiple bits to reflect thesystem information configuration or the change in the systeminformation. The system information configuration or the change in thesystem information configuration may be determined by MTC informationprocessing module 420 and/or receiver 410 utilizing the counter receivedover the paging channel.

In some embodiments, MTC information processing module 420 and/orreceiver 410 may be configured to determine a sleep time of the MTCdevice exceeds a time duration. A system information block may be read(e.g., decoded) by MTC information processing module 420 and/or receiver410 when the determined sleep time exceeds the time duration.

Turning next to FIG. 5, a block diagram illustrates a system 500configured for facilitating Machine Type Communication (MTC) in awireless communications system in accordance with various embodiments.System 500 may include a device 300-a, which may be an example of device300 of FIG. 3, and a device 400-a, which may be an example of device 400of FIG. 4. Devices 300-a and/or 400-a may also be processors. Device300-a and device 400-a may be in wireless communication with each otheras part of facilitating the Machine Type Communication.

Device 300-a may include receiver 310, MTC physical broadcast channelmodule 320-a, and/or transmitter 330. Each of these components may be incommunication with each other. In some cases, these components may beintegrated with each other; for example, MTC physical broadcast channelmodule 320-a may be integrated transmitter 330. MTC physical broadcastchannel module 320-a may include MTC-PBCH configuration module 321,MTC-PBCH payload reduction module 322, MTC-PBCH paging indication module323, and/or MTC-PBCH system information indication module 324.

Device 400-a may include receiver 410, MTC physical broadcast channelprocessing module 420-a, and/or transmitter 430. Each of thesecomponents may be in communication with each other. In some cases, thesecomponents may be integrated with each other; for example, MTC physicalbroadcast channel processing module 420-a may be integrated receiver410. MTC physical broadcast channel processing module 420-a may includeMTC-PBCH information processing module 421, MTC-PBCH paging indicationreceiving module 423, and/or MTC-PBCH system information indicationreceiving module 424.

These components of the devices 300-a and/or 400-a may, individually orcollectively, be implemented with one or more application-specificintegrated circuits (ASICs) adapted to perform some or all of theapplicable functions in hardware. Alternatively, the functions may beperformed by one or more other processing units (or cores), on one ormore integrated circuits. In other embodiments, other types ofintegrated circuits may be used (e.g., Structured/Platform ASICs, FieldProgrammable Gate Arrays (FPGAs), and other Semi-Custom ICs), which maybe programmed in any manner known in the art. The functions of each unitmay also be implemented, in whole or in part, with instructions embodiedin a memory, formatted to be executed by one or more general orapplication-specific processors. Each of the noted modules may be ameans for performing one or more functions related to operation of thedevices 300-a and/or 400-a.

In some embodiments, MTC physical broadcast channel module 320-a throughMTC-PBCH configuration module 321 and/or transmitter 330 of device 300-amay configure information to transmit over an MTC physical broadcastchannel to device 400-a. The information may be transmitted over the MTCphysical broadcast channel through transmitter 330. In some cases, theinformation is transmitted to multiple devices, like device 400-a. Forexample, MTC physical broadcast channel processing module 420-a throughMTC-PBCH information processing module 421 and/or receiver 410 of device400-a may be configured to receive the information transmitted over anMTC physical broadcast channel. The information received over the MTCphysical broadcast channel may be processed by MTC physical broadcastchannel processing module 420-a through MTC-PBCH information processingmodule 421 and/or receiver 410 of device 400-a.

In some embodiments, MTC physical broadcast channel is transmittedwithin a subframe separate from a regular physical broadcast channel.For example, the MTC physical broadcast channel may be transmittedwithin the fifth subframe (SF5) of a frame. And it may be transmittedwithin the center six RBs.

In some cases, the information is transmitted multiple times within aframe. For example, the same MTC physical broadcast channel may berepeated within a 10 ms frame, which may result in better link budget.In some cases, bundled transmission of MTC physical broadcast channelswith extended transmission time intervals (TTI) (e.g., multiplesubframes/symbols) may be utilized within a 10 ms frame. SF5 may bechosen since a cell-specific reference signal (CRS) may only be presentin SF0 and SF5; but other subframes may be chosen as well for the MTCphysical broadcast channel. In some cases, the MTC physical broadcastchannel location may be a function of a physical cell identification(PCI or cell ID) and/or cyclic prefix (CP) length. In some embodiments,an MTC physical broadcast channel is rate-matched around CRS, assuming afixed number of transmit antenna ports, for instance, always assumesfour transmit antennas. In some embodiments, single transmission for oneantenna or space-frequency block coding (SFBC) for two (2) and four (4)antennas is utilized. Some embodiments may result in a reduced number ofblind decodes, from three (3) to two (2), for example.

In some embodiments, MTC physical broadcast channel module 320-a throughMTC-PBCH payload reduction module 322 and/or transmitter 330 of device300-a may configure the information to transmit over the MTC physicalbroadcast channel to reduce a payload for the MTC physical broadcastchannel. For example, the payload of the MTC physical broadcast channelmay be reduced as compared with a typical LTE/LTE-A PBCH. Reducing thepayload for the MTC physical broadcast channel may include reducing thenumber of bits utilized to reflect a downlink bandwidth, a system framenumber, a PHICH duration, a PHICH group, one or more reserved bits, or acyclic redundancy check. This reduction in physical broadcast channelpayload may be referred to as “removing” aspects of a typical, or“regular” PBCH. MTC physical broadcast channel processing module 420-athrough MTC-PBCH information processing configuration module 421 and/orreceiver 410 of device 400-a may be configured to receive the reducedpayload transmitted over the MTC physical broadcast channel.

In some embodiments, payload reduction implemented MTC physicalbroadcast channel module 320-a through MTC-PBCH payload reduction module322 and/or transmitter 330 of device 300-a includes removing downlinkbandwidth (DL BW) bits, which may generally have three (3) bits. Forexample, device 300-a and/or device 400-a may support narrowbandoperation of 1.4 MHz regardless of system bandwidth for regularservices. In some embodiment, device 300-a and/or device 400-a supportsnarrowband operation at least in the cell search, in which casebandwidth information may be signaled at a later stage during connectionsetup.

Payload reduction implemented through MTC-PBCH payload reduction module322 and/or transmitter 330 of device 300-a may include removing PHICHduration bits (which generally includes 1 bit) and PHICH groups bits(which generally includes two (2) bits). Some examples include utilizinga HARQ-less operation. Devices 300-a and/or 400-a that may utilize afixed PHICH duration and PHICH group in MTC subframes in some cases.

Payload reduction implemented through MTC-PBCH payload reduction module322 and/or transmitter 330 of device 300-a may include removing orreducing reserved bits from ten (10) bits. In some embodiments, cyclicredundancy check (CRC) bits may be kept the same (typically 16 bits) orreduced to smaller CRC (e.g., 8 bits).

In some embodiments, payload reduction is implemented MTC physicalbroadcast channel module 320-a through MTC-PBCH payload reduction module322 and/or transmitter 330 of device 300-a includes indicating anMTC-specific system information block (SIB) location over the MTCphysical broadcast channel. MTC-PBCH payload reduction module 322 and/ortransmitter 330 of device 300-a may be configured to transmit an MTCsystem frame number (SFN) over the MTC physical broadcast channel, whichmay be received and/or processed by receiver 410 and/or MTC-PBCHinformation processing module 421 of device 400-a. The MTC system framenumber may map to a longer frame length than a regular system framenumber in some cases.

For example, SFNs generally include 8 bits plus 2 bits for blind decode.In some embodiments MTC physical broadcast channel may contain SFN. Thismay be similar to regular UE operation for determining SIB and/or paginglocation. In some embodiments, MTC physical broadcast channel may notcontain SFN, but it may include one or more bits to indicate theMTC-specific system information block location. For example, 2 bits maybe utilized to indicate four (4) possible locations of MTC-specificsystem information blocks relative to the regular PBCH. In someembodiments, a single bit could be utilized to indicate whether a SIB ispresent in the current radio frame or MTC radio frame. In someembodiments, a different MTC system frame number may be transmitted,which has larger granularity. SFN generally has 10 ms of frame length;MTC SFN may, for example, have a 40 ms frame length. More repetition forthe MTC physical broadcast channel within the MTC SFN may be utilized asa result, and the SFN may be reduced, by 2 bits for instance.

In some embodiments, an MTC physical broadcast channel may be utilizedfor other purposes. For example, MTC physical broadcast channel module320-a through MTC-PBCH paging indication module 323 and/or transmitter330 of device 300-a may configure information to transmit over the MTCphysical broadcast channel that may include a paging indicator. In somecases, the paging indicator includes an individual bit to indicatewhether there is paging for at least one MTC device. In other scenarios,the paging indicator may include multiple bits to indicate whether thereis paging for multiple different paging groups.

MTC physical broadcast channel processing module 420-a through MTC-PBCHpaging indication receiving module 423 and/or receiving 410 of device400-a may receive and utilize this paging indication received over theMTC physical broadcast channel. For example, at each wake up, MTCdevices 115 through device 400-a may only monitor MTC physical broadcastchannel. Paging may be indicated through the MTC physical broadcastchannel. In one set of embodiments, a single bit may indicate if thereis paging for any MTC devices 115. If there is paging, MTC devices 115through device 400-a, in some cases, may try a paging channel. If thereis no paging, MTC device 115 may go back to sleep after reading (e.g.,decoding) the MTC physical broadcast channel. Some embodiments utilizemore than one (1) bit, where multiple MTC devices 115 (or devices 400-a)may be split into different paging groups (e.g., four (4) bits for four(4) paging groups).

In some embodiments, MTC physical broadcast channel module 320-a throughMTC-PBCH system information indication module 324 and/or transmitter 330of device 300-a may configure information to transmit over the MTCphysical broadcast channel that may include a system information changeindicator. MTC physical broadcast channel processing module 420-athrough MTC-PBCH system information indication receiving module 424and/or receiving 410 of device 400-a may receive and/or utilize thesystem indication change indicator. The system information changeindicator may utilize a counter. For example, if MTC-PBCH systeminformation indication receiving module 424 and/or receiving 410 ofdevice 400-a finds the counter to be the same as the last wake up, thismay reflect that there is no system information update. Otherwise,device 400-a may decode MTC-specific system information blocks if aconnection may be needed.

In some embodiments, MTC physical broadcast channel module 320-a throughMTC-PBCH system information indication module 324 and/or transmitter 330of device 300-a may configure information to transmit over the MTCphysical broadcast channel. For instance, a PDCCH or an ePDCCHconfiguration indicator may be created and transmitted over the MTCphysical broadcast channel. This information may be utilized for SIBscheduling. In some cases, the starting point of ePDCCH depends, forexample, on legacy control channel length. In some cases, theconfiguration may be fixed, which may be at the cost of lost dimensions.In other cases, the configuration may be signaled in PBCH, which mayallow better utilization of resources. For example, indicating the PDCCHand/or ePDCCH configuration may include a starting position and/or afrequency location for ePDCCH and/or starting and ending position fornarrowband PDCCH. PDCCH may include narrowband PDCCH that may be shiftedfrom the legacy wideband PDCCH region, but time-division multiplexedwith data. ePDCCH may include the narrowband ePDCCH that may befrequency-division multiplexed with data.

Turning next to FIG. 6, a block diagram illustrates a system 600configured for facilitating Machine Type Communication (MTC) in awireless communications system in accordance with various embodiments.System 600 may include a device 300-b, which may be an example of device300 of FIG. 3, and a device 400-b, which may be an example of device 400of FIG. 4. Devices 300-b and/or 400-b may also be processors. Device300-b and device 400-b may be in wireless communication with each otheras part of facilitating the Machine Type Communication.

Device 300-b may include receiver 310, MTC system information blockmodule 320-b, and/or transmitter 330. Each of these components may be incommunication with each other. In some cases, these components may beintegrated with each other; for example, MTC system information blockmodule 320-b may be integrated transmitter 330. MTC system informationblock module 320-b a may include MTC-SIB configuration module 325 and/orMTC-PBCH SIB conveyance module 326.

Device 400-b may include receiver 410, MTC system information blockmodule 420-b, and/or transmitter 430. Each of these components may be incommunication with each other. In some cases, these components may beintegrated with each other; for example, MTC system information blockmodule 420-b a may be integrated receiver 410. MTC system informationblock module 420-b may include MTC-SIB information processing module 425and/or MTC-SIB location determination module 426.

These components of the devices 300-b and/or 400-b may, individually orcollectively, be implemented with one or more application-specificintegrated circuits (ASICs) adapted to perform some or all of theapplicable functions in hardware. Alternatively, the functions may beperformed by one or more other processing units (or cores), on one ormore integrated circuits. In other embodiments, other types ofintegrated circuits may be used (e.g., Structured/Platform ASICs, FieldProgrammable Gate Arrays (FPGAs), and other Semi-Custom ICs), which maybe programmed in any manner known in the art. The functions of each unitmay also be implemented, in whole or in part, with instructions embodiedin a memory, formatted to be executed by one or more general orapplication-specific processors. Each of the noted modules may be ameans for performing one or more functions related to operation of thedevices 300-b and/or 400-b.

In some embodiments, MTC system information block module 320-b throughMTC-SIB configuration module 325 and/or transmitter 330 of device 300-bmay configure one or more MTC-specific system information blocks. MTCsystem information block module 320-b through MTC-SIB configurationmodule 325 and/or transmitter 330 may transmit the one or moreMTC-specific system information blocks to device 400-b. Device 400-b,through receiver 410 and/or MTC system information block module 420-bthrough MTC-SIB information processing module 425, may receive and/orprocess the one or more MTC-specific system information blocks.

Configuring the one or more MTC-specific system information blocks usingMTC system information block module 320-b through MTC-SIB configurationmodule 325 and/or transmitter 330 of device 300-b may include combiningsystem information (e.g., fields) from several other SIBs into one ofthe one or more MTC-specific system information blocks. Additionally oralternatively, an MTC-specific system information block may consist of asubset of information available in another system information block. Insome embodiments, MTC system information block module 320-b throughMTC-SIB configuration module 325 and/or transmitter 330 of device 300-bmay be configured to utilize one or more MTC fields as part of the oneor more MTC-specific system information blocks to replace one or moreregular fields from one or more other SIBs.

In some embodiments, multiple SIBs may be combined and simplified intoone or more MTC-specific system information blocks utilizing MTC systeminformation block module 320-b through MTC-SIB configuration module 325and/or transmitter 330 of device 300-b. For example, SIB1 generallyincludes access information and scheduling information for other SIBs.SIB2 generally includes common and shared channel information. SIB12generally includes extended access barring (EBA) information for MTC.MTC system information block module 320-b through MTC-SIB configurationmodule 325 and/or transmitter 330 of device 300-b may reduce SIB1 to afirst MTC-specific system information block through supporting themandatory list of SIB1, while scheduling information for other SIBs maybe reduced to one optional, second MTC-specific system information blockfor future usage. Some embodiments may reduce SIB2, which may includeintroducing new fields to replace old fields (e.g., MTC_RACH, MTC_page),while utilizing a simplified design with PUSCH, power control, and/or atimer, and removing some channels, such as PUCCH and/or SRS. In someembodiments, the MTC-specific system information blocks may include theEBA information from SIB12.

In some cases, the one or more MTC-specific system information blocksutilized by devices 300-b and/or 400-b are located at one or morepredetermined locations within an LTE/LTE-A subframe. MTC-specificsystem information blocks may be configured with predetermined resourcesblocks (RB) and/or modulation and coding schemes (MCS). In some cases,the subframe location and/or RB may be a function of cell ID. They mayalso be a function of division duplex configuration, such as FrequencyDivision Duplex (FDD) versus Time Division Duplex (TDD). The locationand/or RB of the MTC-specific system information block may be a functionof cyclic prefix (CP) length, such as normal CP (NCP) versus extended CP(ECP). Some embodiments include utilizing an MTC physical broadcastchannel to convey information regarding one or more locations of the oneor more MTC-specific system information blocks utilizing the MTC-PBCHSIB conveyance module 326 of device 300-b. The MTC-SIB locationdetermination module 426 of device 400-b may utilize this information todetermine the location of the MTC SIBs. For example, the MTC physicalbroadcast channel may convey SIB1 configuration information, which mayinclude timing and/or RB information for an MTC-specific systeminformation block.

Turning next to FIG. 7, a block diagram illustrates a system 700configured for facilitating Machine Type Communication (MTC) in awireless communications system in accordance with various embodiments.System 700 may include a device 300-c, which may be an example of device300 of FIG. 3, and a device 400-c, which may be an example of device 400of FIG. 4. Devices 300-c and/or 400-c may also be processors. Device300-c and device 400-c may be in wireless communication with each otheras part of facilitating the Machine Type Communication.

Device 300-c may include receiver 310, MTC system information indicationmodule 320-c, and/or transmitter 330. Each of these components may be incommunication with each other. In some cases, these components may beintegrated with each other; for example, MTC system informationindication module 320-c may be integrated transmitter 330. MTC systeminformation indication module 320-cmay include MTC-SIB determinationmodule 327 and/or MTC-SIB update counter module 328.

Device 400-c may include receiver 410, MTC system information updatedetermination module 420-c, and/or transmitter 430. Each of thesecomponents may be in communication with each other. In some cases, thesecomponents may be integrated with each other; for example, MTC systeminformation update determination module 420-c may be integrated receiver410. MTC system information update determination module 420-c mayinclude MTC timing module 427 and/or MTC-SIB update counterdetermination module 428.

These components of the devices 300-c and/or 400-c may, individually orcollectively, be implemented with one or more application-specificintegrated circuits (ASICs) adapted to perform some or all of theapplicable functions in hardware. Alternatively, the functions may beperformed by one or more other processing units (or cores), on one ormore integrated circuits. In other embodiments, other types ofintegrated circuits may be used (e.g., Structured/Platform ASICs, FieldProgrammable Gate Arrays (FPGAs), and other Semi-Custom ICs), which maybe programmed in any manner known in the art. The functions of each unitmay also be implemented, in whole or in part, with instructions embodiedin a memory, formatted to be executed by one or more general orapplication-specific processors. Each of the noted modules may be ameans for performing one or more functions related to operation of thedevices 300-c and/or 400-c.

In some embodiments, MTC system information indication module 320-cthrough MTC-SIB determination module 327 and/or transmitter module 330may determine a system information configuration from multiple systeminformation configurations. A counter may be configured and/ortransmitted through MTC-SIB update counter module 328 and/or transmitter330 to indicate the system information configuration or a change in thesystem information configuration. The counter may include one or morebits to reflect the system information configuration or the change inthe determined system information. MTC system information updatedetermination module 420-c through MTC-SIB update counter determinationmodule 428 and/or receiver module 410 of device 400-c may be configuredto receive the counter to indicate the system information configurationor a change in the system information configuration. The systeminformation configuration or a change in the system informationconfiguration may be determined by MTC-SIB update counter determinationmodule 428 and/or receiver module 410 of device 400-c utilizing thecounter received over the paging channel.

For example, a counter may be added to a page to indicate the systeminformation update utilizing multiple bits. Device 400-c may wake upinfrequently to receive and read the counter. If the received counter isdifferent from the previous wake up, device 400-c may determine that thesystem information has changed. For instance, the counter could beincremented (e.g., incremented by a count of one (1)) whenever thesystem information changes. The device 400-c may thus be configured todetermine system information has changed since a previous wake-up if itreceives an incremented counter. In some cases, the counter may indicateboth a change in system information configuration and an updated systeminformation configuration. For example, the counter may include four (4)bits to map to sixteen (16) different system information configurations,which the device 400-c may be configured to identify.

In various embodiments, the device 300-c may convey, and the device400-c may receive, a counter over different channels. For example, thecounter may be conveyed and received over a paging channel, over PBCH,or over an MTC physical broadcast channel. The counter may also beincluded in, and decoded from, a SIB, such as an MTC-specific SIB.

In some embodiments, MTC system information update determination module420-c through MTC timing module 427 and/or receiver module 410 of device400-c may be configured to determine a sleep time of the MTC deviceexceeds a time duration. A system information block may be read by MTCsystem information update determination module 420-c and/or receiver 410when the determined sleep time exceeds the time duration. For example,if device 400-c has a sleep time that exceeds a specific time duration,it may assume that the system information has changed, and it may read aSIB (e.g., an MTC-specific SIB) upon making such a determination. Insome cases, the device 400-c is programmed with a sleep time duration,which may be on the order of seconds, minutes, or longer.

FIG. 8 shows a block diagram of a communications system 800 configuredto facilitate Machine Type Communication with MTC device(s) 115-c inaccordance with various embodiments. This system 800 may be an exampleof aspects of the system 100 depicted in FIG. 1 and/or system 200 ofFIGS. 2A and 2B. System 800 may include a base station 105-c. The basestation 105-c may include antenna(s) 845, a transceiver module 850, aprocessor module 870, and memory 880, which each may be incommunication, directly or indirectly, with each other (e.g., over oneor more buses). The transceiver module 850 may be configured tocommunicate bi-directionally, via the antenna(s) 845, with the MTCdevice 115-c, which may be a multi-mode MTC device. The transceivermodule 850 (and/or other components of the base station 105-c) may alsobe configured to communicate bi-directionally with one or more networks.In some cases, the base station 105-c may communicate with the corenetwork 130-a and/or controller 120-a through network communicationsmodule 875. Base station 105-c may be an example of an eNodeB basestation, a Home eNodeB base station, a NodeB base station, and/or a HomeNodeB base station. Controller 120-a may be integrated into base station105-c in some cases, such as with an eNodeB base station.

Base station 105-c may also communicate with other base stations 105,such as base station 105-m and base station 105-n. Each of the basestations 105 may communicate with MTC device 115-c using differentwireless communications technologies, such as different Radio AccessTechnologies. In some cases, base station 105-c may communicate withother base stations such as 105-m and/or 105-n utilizing base stationcommunication module 865. In some embodiments, base stationcommunication module 865 may provide an X2 interface within an LTE/LTE-Awireless communication technology to provide communication between someof the base stations 105. In some embodiments, base station 105-c maycommunicate with other base stations through controller 120-a and/orcore network 130-a.

The memory 880 may include random access memory (RAM) and read-onlymemory (ROM). The memory 880 may also store computer-readable,computer-executable software code 885 containing instructions that areconfigured to, when executed, cause the processor module 870 to performvarious functions described herein (e.g., processing of communicationsfrom MTC device 115-c, message routing, etc.). Alternatively, thesoftware code 885 may not be directly executable by the processor module870 but may be configured to cause the computer, e.g., when compiled andexecuted, to perform functions described herein.

The processor module 870 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The transceiver module 850 may include amodem configured to modulate the packets and provide the modulatedpackets to the antenna(s) 845 for transmission, and to demodulatepackets received from the antenna(s) 845. While some examples of thebase station 105-c may include a single antenna 845, the base station105-c may include multiple antennas 845 for multiple links which maysupport carrier aggregation. For example, one or more links may be usedto support macro communications with MTC device 115-c.

According to the architecture of FIG. 8, the base station 105-c mayfurther include a communications management module 860. Thecommunications management module 860 may manage communications withother base stations 105. By way of example, the communicationsmanagement module 860 may be a component of the base station 105-c incommunication with some or all of the other components of the basestation 105-c via a bus. Alternatively, functionality of thecommunications management module 860 may be implemented as a componentof the transceiver module 850, as a computer program product, and/or asone or more controller elements of the processor module 870.

The base station 105-c may be configured to implement aspects discussedabove with facilitating Machine Type Communication with respect todevices 300 of FIGS. 3, 5, 6, and/or 7 and may not e repeated here forthe sake of brevity. For example, base station 105-c may include an MTCPBCH module 320-a-i, which may be an example of the MTC informationconfiguration module 320 of FIG. 3 and/or the MTC physical broadcastchannel module 320-a of FIG. 5. The base station 105-c may include anMTC SIB module 320-b-i, which may be an example of the MTC informationconfiguration module 320 of FIG. 3 and/or the MTC system informationblock module 320-b of FIG. 6. The base station 105-c may include an MTCsystem information indication module 320-c-i, which may be an example ofMTC information configuration module 320 of FIG. 3 and/or the MTC systeminformation indication module 320-c of FIG. 7.

Components of base station 105-c may, individually or collectively, beimplemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors. Each of the noted modules may be ameans for performing one or more functions related to operation of thebase station 105-c.

FIG. 9 is a block diagram 900 of an MTC device 115-d configured forfacilitating Machine Type Communication in accordance with variousembodiments. The MTC device 115-d may have any of various configurationsand be coupled with one or more other devices, as discussed above, tosense one or more conditions related to a monitor, meter, and/or otherdevice associated with the MTC device 115-d. The MTC device 115-d mayhave an internal power supply (not shown), such as a small battery, tofacilitate mobile operation. In some embodiments, the MTC device 115-dmay be an MTC device 115 of FIG. 1, FIG. 2A, FIG. 2B, FIG. 8, and/orFIG. 10. The MTC device 115-d may be referred to as an MTC UE or M2Mdevice, in some cases.

The MTC device 115-d may include a sensor 915 in some embodiments. MTCdevice 115-d also includes antenna(s) 945, a transceiver module 950, aprocessor module 970 and memory 980, which each may be in communication,directly or indirectly, with each other (e.g., via one or more buses).The transceiver module 950 may be configured to communicatebi-directionally, via the antenna(s) 945 and/or one or more wired orwireless links, with one or more networks, as described above. Forexample, the transceiver module 950 may be configured to communicatebi-directionally with base stations 105 of FIG. 1, FIG. 2A, FIG. 2B,FIG. 8, and/or FIG. 10. The transceiver module 950 may include a modemconfigured to modulate the packets and provide the modulated packets tothe antenna(s) 945 for transmission, and to demodulate packets receivedfrom the antenna(s) 945. While the MTC device 115-d may include a singleantenna 945, the MTC device 115-d may include multiple antennas 945 formultiple transmission links.

The memory 980 may include random access memory (RAM) and read-onlymemory (ROM). The memory 980 may store computer-readable,computer-executable software code 985 containing instructions that areconfigured to, when executed, cause the processor module 970 to performvarious functions described herein (e.g., process MTC-specific systeminformation blocks, determine sleep times, determine system informationconfigurations or changes in system information configurations, etc.).Alternatively, the software code 985 may not be directly executable bythe processor module 970 but may be configured to cause the computer(e.g., when compiled and executed) to perform functions describedherein.

The processor module 970 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. According to the architecture of FIG. 9,the mobile device 115-d may further include a communications managementmodule 960. The communications management module 960 may managecommunications with base stations 105 and/or other MTC devices 115. Byway of example, the communications management module 960 may be acomponent of the MTC device 115-d in communication with some or all ofthe other components of the mobile device 115-d via a bus.Alternatively, functionality of the communications management module 960may be implemented as a component of the transceiver module 950, as acomputer program product, and/or as one or more controller elements ofthe processor module 970.

The MTC device 115-d may be configured to facilitate Machine TypeCommunication as discussed with respect to devices 400 of FIGS. 4, 5, 6,and/or 7 and may not be repeated here for the sake of brevity. Forexample, the MTC device 115-d may include an MTC PBCH processing module420-a-i, which may be an example of the MTC information processingmodule 420 of FIG. 4 and/or the MTC physical broadcast channelprocessing module 420-a of FIG. 5. The MTC device 115-d may include anMTC SIB module 420-b-i, which may be an example of the MTC informationprocessing module 420 of FIG. 4 and/or the MTC system information blockmodule 420-b of FIG. 6. The MTC device 115-d may include an MTC systeminformation update determination module 420-c-i, which may be an exampleof MTC information processing module 420 of FIG. 4 and/or the MTC systeminformation update determination module 420-c of FIG. 7.

Components of MTC device 115-d may, individually or collectively, beimplemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors. Each of the noted modules may be ameans for performing one or more functions related to operation of theMTC device 115-d.

FIG. 10 is a block diagram of a system 1000 including a base station105-d and a mobile device 115-e in accordance with various embodiments.This system 1000 may be an example of the system 100 of FIG. 1, system200-a of FIG. 2A, system 200-b of FIG. 2B, system 500 of FIG. 5, system600 of FIG. 6, system 700 of FIG. 7, and/or system 800 of FIG. 8. Thebase station 105-d may be equipped with antennas 1034-a through 1034-x,and the mobile device 115-e may be equipped with antennas 1052-a through1052-n. At the base station 105-f, a transmit processor 1020 may receivedata from a data source.

The transmitter processor 1020 may process the data. The transmitterprocessor 1020 may also generate reference symbols, and a CRS. Atransmit (TX) MIMO processor 1030 may perform spatial processing (e.g.,precoding) on data symbols, control symbols, and/or reference symbols,if applicable, and may provide output symbol streams to the transmitmodulators 1032-a through 1032-x. Each modulator 1032 may process arespective output symbol stream (e.g., for OFDM, etc.) to obtain anoutput sample stream. Each modulator 1032 may further process (e.g.,convert to analog, amplify, filter, and upconvert) the output samplestream to obtain a downlink (DL) signal. In one example, DL signals frommodulators 1032-a through 1032-x may be transmitted via the antennas1034-a through 1034-x, respectively. The transmitter processor 1020 mayreceive information from a processor 1040. In some embodiments, theprocessor 1040 may be implemented as part of a general processor, thetransmitter processor 1020, and/or the receiver processor 1038. A memory1042 may be coupled with the processor 1040.

In some embodiments, the processor 1040 and/or MTC informationconfiguration module 1044 are configured to communicate with MTC device115-e. The processor 1040 and/or MTC information configuration module1044 may configure information to transmit over an MTC physicalbroadcast channel. The information may be transmitted over the MTCphysical broadcast channel through transmitters 1032. In some cases, theinformation may be transmitted to multiple MTC devices.

In some embodiments, MTC physical broadcast channel is transmittedwithin a subframe separate from a regular physical broadcast channel.The MTC physical broadcast channel may be transmitted within a fifthsubframe (SF5) of a frame, and within the center six (6) RBs. In somecases, the information is transmitted multiple times within a frame.

The processor 1040 and/or MTC information configuration module 1044 mayconfigure the information to transmit over the MTC physical broadcastchannel to include reducing a payload for the MTC physical broadcastchannel with respect to a regular physical broadcast channel. Reducingthe payload for the MTC physical broadcast channel may include removingone or more bits utilized to reflect a downlink bandwidth, a systemframe number, a physical hybrid ARQ indicator channel (PHICH) duration,a PHICH group, one or more reserved bits, or a cyclic redundancy checkwith respect to the regular physical broadcast channel.

The processor 1040 and/or MTC information configuration module 1044 maybe configured to indicate an MTC-specific system information blocklocation over the MTC physical broadcast channel. The processor 1040and/or MTC information configuration module 1044 may be configured totransmit an MTC system frame number over the MTC physical broadcastchannel. The MTC system frame number may map to a longer frame lengththan a regular system frame number.

Configuring the information to transmit over the MTC physical broadcastchannel through the processor 1040 and/or MTC information configurationmodule 1044 may include configuring a paging indicator to transmit overthe MTC physical broadcast channel. The paging indicator may include anindividual bit to indicate whether there is paging for at least one MTCdevice in some cases. The paging indicator may include multiple bits toindicate whether there is paging for multiple different paging groups inother cases. Configuring the information to transmit over the MTCphysical broadcast channel may include configuring a system informationchange indicator, such as a counter, to transmit over the MTC physicalbroadcast channel.

In some embodiments, the processor 1040 and/or MTC informationconfiguration module 1044 may configure one or more MTC-specific systeminformation blocks. The transmitters 1032 may transmit the one or moreMTC-specific system information blocks to multiple MTC devices.

Configuring the one or more MTC system information blocks through theprocessor 1040 and/or MTC information configuration module 1044 mayinclude combining a portion from each of multiple other systeminformation blocks into at least one of the one or more MTC systeminformation blocks. Combining the portion from each of the multipleregular system information blocks into MTC-specific system informationblocks may include removing another portion from one of the other systeminformation blocks. Or it may involve selecting a subset of systeminformation from another system information block.

The processor 1040 and/or MTC information configuration module 1044 maybe configure to utilize one or more MTC fields as part of theMTC-specific system information blocks to replace fields from othersystem information blocks.

In some cases, MTC-specific system information blocks are located at oneor more predetermined locations. The predetermined locations may be afunction of a cell ID, a cyclic prefix length, or a division duplexconfiguration. Some embodiments include utilizing an MTC physicalbroadcast channel to convey information regarding one or more locationsof the one or more MTC system information blocks.

In some embodiments, the processor 1040 and/or MTC informationconfiguration module 1044 may determine a system informationconfiguration from multiple system information configurations. A countermay be configured and/or transmitted through the processor 1040 and/orMTC information configuration module 1044 to be transmitted to indicatethe system information configuration or a change in the systeminformation configuration. The counter may include multiple bits toreflect determined system information configuration or the change in thedetermined system information.

At the MTC device 115-e, the mobile device antennas 1052-a through1052-n may receive the DL signals from the base station 105-d and mayprovide the received signals to the demodulators 1054-a through 1054-n,respectively. Each demodulator 1054 may condition (e.g., filter,amplify, downconvert, and digitize) a respective received signal toobtain input samples. Each demodulator 1054 may further process theinput samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMOdetector 1056 may obtain received symbols from all the demodulators1054-a through 1054-n, perform MIMO detection on the received symbols ifapplicable, and provide detected symbols. A receiver processor 1058 mayprocess (e.g., demodulate, deinterleave, and decode) the detectedsymbols, providing decoded data for the MTC device 115-e to a dataoutput, and provide decoded control information to a processor 1080, ormemory 1082.

On the uplink (UL), at the MTC device 115-e, a transmitter processor1064 may receive and process data from a data source. The transmitterprocessor 1064 may also generate reference symbols for a referencesignal. The symbols from the transmitter processor 1064 may be precodedby a transmit MIMO processor 1066 if applicable, further processed bythe demodulators 1054-a through 1054-n (e.g., for SC-FDMA, etc.), and betransmitted to the base station 105-d in accordance with thetransmission parameters received from the base station 105-f. Thetransmitter processor 1064 may be configured to obtain information froma sensor, meter, or other device associated with the MTC device 115-eand package the information for transmission in accordance with theembodiments described above. At the base station 105-d, the UL signalsfrom the MTC device 115-e may be received by the antennas 1034,processed by the demodulators 1032, detected by a MIMO detector 1036 ifapplicable, and further processed by a receive processor. The receiveprocessor 1038 may provide decoded data to a data output and to theprocessor 1080. In some embodiments, the processor 1080 may beimplemented as part of a general processor, the transmitter processor1064, and/or the receiver processor 1058.

In some embodiments, the processor 1080 and/or the MTC informationprocessing module 1084 may be configured to receive informationtransmitted over an MTC physical broadcast channel. The informationreceived over the MTC physical broadcast channel may be processed by theprocessor 1080 and/or the MTC information processing module 1084

In some cases, the information transmitted over the MTC physicalbroadcast channel is received within a subframe separate from a regularphysical broadcast channel. The information transmitted over the MTCphysical broadcast channel may be received within the fifth subframe(SF5) of a frame, for example. The information transmitted over the MTCphysical broadcast channel may be received within the center six (6) RBsof the subframe. In some cases, the information may be received multipletimes within a frame.

The information may include a reduced payload for the MTC physicalbroadcast channel with respect to a regular physical broadcast channel.The reduced payload for the MTC physical broadcast channel may include areduced number of one or more bits utilized to reflect a downlinkbandwidth, a system frame number, a physical hybrid ARQ indicatorchannel (PHICH) duration, a PHICH group, one or more reserved bits, or acyclic redundancy check with respect to the regular physical broadcastchannel.

The processor 1080 and/or the MTC information processing module 1084 maybe configured to receive an MTC system information block location overthe MTC physical broadcast channel. MTC information processing module1084 and/or receiver processor 1058 may be configured to receive an MTCsystem frame number over the MTC physical broadcast channel. The MTCsystem frame number may map to a longer frame length than a regularsystem frame number.

Receiving the information transmitted over the MTC physical broadcastchannel at the processor 1080 and/or the MTC information processingmodule 1084 may include receiving an indicator transmitted over the MTCphysical broadcast channel. The indicator may include an individual bitto indicate whether there is paging for the MTC device 115-e. The pagingindicator may include multiple bits to indicate whether there is pagingfor a plurality of different paging groups. Receiving the informationtransmitted over the MTC physical broadcast channel may includereceiving a system information change indicator, such as a counter,transmitted over the MTC physical broadcast channel.

In some embodiments, the processor 1080 and/or the MTC informationprocessing module 1084 may be configured to receive one or more MTCsystem information blocks. The one or more MTC system information blocksmay be processed at the processor 1080 and/or the MTC informationprocessing module 1084

Receiving the one or more MTC-specific system information blocks at theprocessor 1080 and/or the MTC information processing module 1084 mayinclude receiving a portion from each of several other systeminformation blocks combined into one or more MTC-specific systeminformation blocks. The MTC-specific system information blocks mayinclude MTC-relevant system information, and they may exclude additionalsystem information. The processor 1080 and/or the MTC informationprocessing module 1084 may be configured to receive one or more MTCfields as part of the one or more MTC system information blocks toreplace one or more fields from one or more of the plurality of regularsystem information blocks.

In some cases, the MTC-specific system information blocks may be locatedat predetermined locations. The predetermined locations may be afunction of a cell ID, a cyclic prefix length, a division duplexconfiguration. The processor 1080 and/or the MTC information processingmodule 1084 may be configured to receive information regarding one ormore locations of the one or more MTC system information blocks over anMTC physical broadcast channel.

In some embodiments, the processor 1080 and/or the MTC informationprocessing module 1084 may be configured to receive a counter over toindicate the system information configuration or a change in the systeminformation configuration. The counter may include multiple bits toreflect the system information configuration or the change in thedetermined system information. The system information configuration or achange in the system information configuration may be determined by theprocessor 1080 and/or the MTC information processing module 1084utilizing the counter received over the paging channel.

In some embodiments, the processor 1080 and/or the MTC informationprocessing module 1084 may be configured to determine a sleep time ofthe MTC device 115-e exceeds a time duration. A system information blockmay be read by the processor 1080 and/or the MTC information processingmodule 1084 when the determined sleep time exceeds the time duration.

FIG. 11A is a flow chart illustrating an example of a method 1100-a forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1100-a is described belowwith reference to devices such as: the base stations 105 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 300 of FIG. 3, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below.

At block 1105, information may be configured to transmit over an MTCphysical broadcast channel. The operations of block 1105 may beperformed by the MTC information configuration module 320 of FIG. 3, theMTC physical broadcast channel module 320-a of FIG. 5, and/or theMTC-PBCH configuration module 321 of FIG. 5. Configuring the informationto transmit over the MTC physical broadcast channel may include reducinga payload for the MTC physical broadcast channel with respect to aregular physical broadcast channel. Reducing the payload for the MTCphysical broadcast channel may include removing, with respect to theregular physical broadcast channel, one or more bits utilized to reflecta downlink bandwidth, a system frame number, a physical hybrid ARQindicator channel (PHICH) duration, a PHICH group, one or more reservedbits, or a cyclic redundancy check.

In some cases, configuring the information to transmit over the MTCphysical broadcast channel may include configuring a paging indicator totransmit over the MTC physical broadcast channel. The paging indicatormay include an individual bit to indicate whether there is paging for atleast one MTC device in some cases. The paging indicator may includemultiple bits to indicate whether there is paging for multiple differentpaging groups in other cases. Configuring the information to transmitover the MTC physical broadcast channel at block 1105 may includeconfiguring a system information change indicator to transmit over theMTC physical broadcast channel. Configuring the information to transmitover the MTC physical broadcast channel may include configuring at leasta PDCCH or an ePDCCH configuration indicator to transmit over the MTCphysical broadcast channel.

At block 1110, the information may be transmitted over the MTC physicalbroadcast channel. In some cases, the information may be transmitted tomultiple MTC devices. The operations of block 1110 are, in variousembodiments, performed by the transmitter 330 of FIG. 3 or 5. In someembodiments, the MTC physical broadcast channel is transmitted within asubframe separate from a regular physical broadcast channel. The MTCphysical broadcast channel may be transmitted within the fifth subframe(SF5) of a frame and/or within the center six (6) RBs. In some cases,the information is transmitted multiple times within a frame.

Some embodiments of method 1100-a include indicating an MTC systeminformation block location over the MTC physical broadcast channel. Someembodiments include transmitting an MTC system frame number over the MTCphysical broadcast channel, where the MTC system frame number maps to alonger frame length than a regular (e.g., legacy) system frame number.

FIG. 11B is a flow chart illustrating an example of a method 1100-b forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1100-b is described belowwith reference to devices such as: the base stations 105 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 300 of FIG. 3, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below. Method 1100-bmay be an example of method 1100-a of FIG. 11A.

At block 1115, a payload of system information for a MTC physicalbroadcast channel may be reduced with respect to a regular physicalbroadcast channel. The operations of block 1105 may be performed by theMTC information configuration module 320 of FIG. 3, the MTC physicalbroadcast channel module 320-a of FIG. 5, and/or the MTC-PBCH payloadreduction module 322 of FIG. 5.

At block 1105-a, the reduced payload may be configured for transmissionover the MTC physical broadcast channel. The operations of block 1105may be performed by the MTC information configuration module 320 of FIG.3, the MTC physical broadcast channel module 320-a of FIG. 5, and/or theMTC-PBCH configuration module 321 of FIG. 5.

At block 1110-a, the reduced payload of system information may betransmitted over the MTC physical broadcast channel to multiple MTCdevices. In some cases, the operations of block 1110-a are performed bythe transmitter 330 of FIG. 3 or 5.

FIG. 12A is a flow chart illustrating an example of a method 1200-a forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1200-a is described belowwith reference to devices such as: the base stations 105 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 300 of FIG. 3, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below.

At block 1205, one or more MTC-specific system information blocks may beconfigured. The operations of block 1205 may be performed by the MTCinformation configuration modules 320 of FIG. 3, the MTC systeminformation block module 320-b of FIG. 6, and/or the MTC-SIBconfiguration module 325 of FIG. 6. Configuring the one or moreMTC-specific system information blocks may include combining at least aportion from each of multiple regular system information blocks into atleast one of the one or more MTC-specific system information blocks.Combining at least the portion from each of the multiple regular systeminformation blocks into at least one of the one or more MTC-specificsystem information blocks may include removing another portion from atleast one of the multiple regular system information blocks.

Some embodiments of method 1200-a include utilizing one or more MTCfields as part of the one or more MTC-specific system information blocksto replace one or more regular fields from one or more of the multiplesystem information blocks. In some cases, the one or more MTC systeminformation blocks are located at one or more predetermined locations.The one or more predetermined locations may be a function of at least acell ID, a cyclic prefix length, or a division duplex configuration.Some embodiments include utilizing an MTC physical broadcast channel toconvey information regarding one or more locations of the one or moreMTC system information blocks.

At block 1210, the one or more MTC-specific system information blocksmay be transmitted to multiple MTC devices. For example, the operationsof block 1210 may be performed by the transmitters 330 of FIGS. 3 and 6.

FIG. 12B is a flow chart illustrating an example of a method 1200-b forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1200-b is described belowwith reference to devices such as: the base stations 105 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 300 of FIG. 3, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below. Method 1200-bmay be an example of method 1200-a of FIG. 12A.

At block 1215, multiple system information blocks may be identified. Theoperations of block 1215 may be performed by the MTC informationconfiguration module 320 of FIG. 3, the MTC system information blockmodule 320-b of FIG. 6, and/or the MTC-SIB configuration module 325 ofFIG. 6.

At block 1220, one or more portions of one or more of the multiplesystem information blocks may be removed. The operations of block 1215may be performed by the MTC information configuration module 320 of FIG.3, the MTC system information block module 320-b of FIG. 6, and/or theMTC-SIB configuration module 325 of FIG. 6.

At block 1205-a, the multiple system information blocks with one or moreportions removed may be configured as one more MTC-specific systeminformation blocks. The operations of block 1215 may be performed by theMTC information configuration module 320 of FIG. 3, the MTC systeminformation block module 320-b of FIG. 6, and/or the MTC-SIBconfiguration module 325 of FIG. 6.

At block 1210-a, the one or more MTC-specific system information blocksmay be transmitted to one or more MTC devices. For example, theoperations of block 1210 may be performed by the transmitters 330 ofFIGS. 3 and 6.

FIG. 13 is a flow chart illustrating an example of a method 1300 forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1300 is described belowwith reference to devices such as: the base stations 105 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 300 of FIG. 3, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below.

At block 1305, a system information configuration may be determined frommultiple system information configurations. The operations of block 1305are, in various embodiments, performed by the MTC informationconfiguration module 320 of FIG. 3, the MTC system informationindication module 320-c of FIG. 7, and/or the MTC-SIB determinationmodule 327 of FIG. 7.

At block 1310, a counter may be transmitted to indicate the systeminformation configuration or a change in the system informationconfiguration. The counter may include multiple bits to reflect at leastthe determined system information configuration or the change in thedetermined system information. The operations of block 1310 may beperformed by the transmitters 330 of FIGS. 3 and 7. In variousembodiments, the counter may be transmitted over a paging channel, overPBCH, and/or over an MTC physical broadcast channel.

FIG. 14A is a flow chart illustrating an example of a method 1400-a forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1400-a is described belowwith reference to devices such as: the MTC devices 115 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 400 of FIG. 4, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below.

At block 1405, information transmitted over an MTC physical broadcastchannel may be received. The operations of block 1405 may be performedby the receivers 410 of FIGS. 4 and 5. In some cases, the informationtransmitted over the MTC physical broadcast channel is received within asubframe separate from a regular physical broadcast channel. Theinformation transmitted over the MTC physical broadcast channel may bereceived within a fifth subframe (SF5) of a frame and/or within thecenter six (6) RBs of the subframe. In some cases, the information maybe received multiple times within a frame.

The information may include a reduced payload for the MTC physicalbroadcast channel with respect to a regular physical broadcast channel.The reduced payload for the MTC physical broadcast channel may include areduced number of one or more bits utilized to reflect a downlinkbandwidth, a system frame number, a physical hybrid ARQ indicatorchannel (PHICH) duration, a PHICH group, one or more reserved bits, or acyclic redundancy check with respect to the regular physical broadcastchannel.

In some cases, receiving the information transmitted over the MTCphysical broadcast channel may include receiving a paging indicator totransmit over the MTC physical broadcast channel. The paging indicatormay include an individual bit to indicate whether there is paging for atleast one MTC device in some cases. The paging indicator may includemultiple bits to indicate whether there is paging for multiple differentpaging groups. Additionally or alternatively, receiving the informationtransmitted over the MTC physical broadcast channel may includereceiving a system information change indicator transmitted over the MTCphysical broadcast channel. Receiving the information transmitted overthe MTC physical broadcast channel at block 1405 may include receivingat least a PDCCH or an ePDCCH configuration indicator transmitted overthe MTC physical broadcast channel

At block 1410, the information received over the MTC physical broadcastchannel may be processed. The operations of block 1410 are, in variousembodiments, performed by the MTC information procession module 420 ofFIG. 4, the MTC physical broadcast channel processing module 420-a ofFIG. 5, and/or the MTC-PBCH information processing module of 421 of FIG.5.

Method 1400-a may include receiving an MTC system information blocklocation over the MTC physical broadcast channel. Method 1400-a mayinclude receiving an MTC system frame number over the MTC physicalbroadcast channel. The MTC system frame number may map to a longer framelength than a regular system frame number.

FIG. 14B is a flow chart illustrating an example of a method 1400-b forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1400-b is described belowwith reference to devices such as: the MTC devices 115 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 400 of FIG. 4, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below. Method 1400-bmay be an example of method 1400-a of FIG. 14A.

At block 1405-a, an MTC-specific system information block location maybe received over an MTC physical broadcast channel. The operations ofblock 1405-a may be performed by the receivers 410 of FIGS. 4 and 5. TheMTC-specific system information blocks may be located at one or morepredetermined locations, which may be a function of a cell ID, a cyclicprefix length, and/or a division duplex configuration.

At block 1410-a, the received MTC-specific system information blocklocation information may be processed to determine a location of one ormore MTC-specific system information blocks. The operations of block1410-a are, in various embodiments, performed by the MTC informationprocession module 420 of FIG. 4, the MTC physical broadcast channelprocessing module 420-a of FIG. 5, and/or the MTC-PBCH informationprocessing module of 421 of FIG. 5.

At block 1415, a reduced payload of system information transmitted overthe MTC physical broadcast channel may be located utilizing thedetermined location of the one or more MTC system information blocks. Invarious embodiments, the operations of block 1415 are performed by theMTC information processing module 420 of FIG. 4, the MTC systeminformation block module 420-b of FIG. 6, and/or the MTC-SIB locationdetermination module 426 of FIG. 6.

FIG. 15A is a flow chart illustrating an example of a method 1500-a forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1500-a is described belowwith reference to devices such as: the MTC devices 115 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 400 of FIG. 4, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below.

At block 1505, one or more MTC system information blocks may be receivedat an MTC device. The operations of block 1505 may be performed by thereceivers of FIGS. 4 and 6.

At block 1510, the one or more MTC system information blocks may beprocessed at the MTC device. In various embodiments, the operations ofblock 1510 may be performed by the MTC information processing module 420of FIG. 4, the MTC system information block module 420-b of FIG. 6,and/or the MTC-SIB information processing module 425 of FIG. 6.

The MTC-specific system information blocks may include a combination ofsystem information included in two or more other system informationblocks. For example, an MTC-specific system information block mayinclude aspects of SIB1, SIB2, and/or SIB12. Additionally oralternatively, an MTC-specific system information block may consist of asubset of system information included in one other system informationblock, such as SIB1, SIB2, or SIB12.

In some embodiments, an MTC-specific system information block includesfields for cell access information, scheduling information for otherSIBs, and radio resource configuration information. In other cases, anMTC-specific system information block includes fields for cell accessinformation and cell selection information, or fields for schedulinginformation for other system information blocks. In still otherembodiments, an MTC-specific system information block includes MTC RACHconfiguration information or MTC paging channel configurationinformation. Or an MTC-specific system information block may consist offields for PUSCH configuration information, power control, and a timer.In other embodiments, an MTC-specific system information block includesfields for radio resource configuration information other than PUSCHconfiguration information and SRS configuration information.

In some cases, the one or more MTC-specific system information blocksmay be located at one or more predetermined locations. The one or morepredetermined locations may be a function of at least a cell ID, acyclic prefix length, a division duplex configuration. Some embodimentsof method 1500-a include receiving information regarding one or morelocations of the one or more MTC-specific system information blocks overan MTC physical broadcast channel.

FIG. 15B is a flow chart illustrating an example of a method 1500-b forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1500-b is described belowwith reference to devices such as: the base stations 105 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 300 of FIG. 3, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below. Method 1200-bmay be an example of method 1500-a of FIG. 15C.

At block 1515, an MTC device may receive information regarding one ormore locations of one or more MTC-specific system information blocksover an MTC physical broadcast channel. The operations of block 1515 maybe performed by the receivers 410 of FIGS. 4 and 5. The MTC-specificsystem information blocks may be located at one or more predeterminedlocations, which may be a function of a cell ID, a cyclic prefix length,and/or a division duplex configuration.

At block 1505-a, one or more MTC system information blocks may bereceived at an MTC device. The operations of block 1505-a may beperformed by the receivers of FIGS. 4 and 6.

At block 1510-a, the one or more MTC system information blocks may beprocessed at the MTC device. In various embodiments, the operations ofblock 1510-a may be performed by the MTC information processing module420 of FIG. 4, the MTC system information block module 420-b of FIG. 6,and/or the MTC-SIB information processing module 425 of FIG. 6.

FIG. 16 is a flow chart illustrating an example of a method 1600 forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1600 is described belowwith reference to devices such as: the MTC devices 115 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 400 of FIG. 4, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below.

At block 1605, a counter may be received to indicate a systeminformation configuration or a change in the system informationconfiguration. The counter may include one or more bits to reflect thesystem information configuration or the change in the system informationconfiguration. The operations of block 1605 may be performed by thereceivers 410 of FIGS. 4 and 7. The counter may include four (4) bitsmapping to sixteen (16) different system information locations. Invarious embodiments, the counter may be received over a paging channel,over PBCH, or over an MTC physical broadcast channel. In some cases, thecounter is received in a SIB, such as an MTC-specific SIB.

At block 1610, the system information configuration or the change in thesystem information configuration may be determined utilizing the counterreceived over the paging channel. The operations of block 1610 may beperformed by the MTC information processing module 420 of FIG. 4, theMTC system information update determination module 420-c of FIG. 7,and/or the MTC-SIB update counter determination module 428 of FIG. 7.Determining the change in the system information configuration mayinclude determining that the receiver counter is different from aprevious wake up. For example, determining the received counter isdifferent from a previous wake up may include receiving an incrementedcounter. Additionally or alternatively, determining the systeminformation configuration or the change in system informationconfiguration may include determining the system information changedbased on the counter and identifying updated system information based onthe counter.

FIG. 17 is a flow chart illustrating an example of a method 1700 forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system. For clarity, the method 1700 is described belowwith reference to devices such as: the MTC devices 115 of FIG. 1, FIG.2A, FIG. 2B, FIG. 8, and/or FIG. 10; and/or devices 400 of FIG. 4, FIG.5, FIG. 6, and/or FIG. 7. In one implementation, a processor may executeone or more sets of codes to control the functional elements of thewireless device to perform the functions described below.

At block 1705, it may be determined at an MTC device whether a sleeptime of the MTC device exceeds a time duration. The operations of block1705 are, in various embodiments, performed by the MTC informationprocessing module 420 of FIG. 4, the MTC system information updatedetermination module 420-c of FIG. 7, and/or the MTC timing module 427of FIG. 7.

At block 1710, at least a system information block may be read when thedetermined sleep time exceeds the time duration. The operations of block1705 are, in various embodiments, performed by the MTC informationprocessing module 420 of FIG. 4, the MTC system information updatedetermination module 420-c of FIG. 7, and/or the MTC timing module 427of FIG. 7.

In some embodiments, the method 1700 is an example of the method 1500-a.For example, an MTC device may perform the operations of blocks 1705 and1710 before performing the operations of blocks 1505 and 1510.

Those skilled in the art will recognize that the methods 1100, 1200,1300, 1400, 1500, 1600, and 1700 are example implementations of thetools and techniques described herein. The methods may be performed withmore or fewer steps; and they may be performed in an order other thanindicated.

The detailed description set forth above in connection with the appendeddrawings describes exemplary embodiments and does not represent the onlyembodiments that may be implemented or that are within the scope of theclaims. The detailed description includes specific details for thepurpose of providing an understanding of the described techniques. Thesetechniques, however, may be practiced without these specific details. Insome instances, well-known structures and devices are shown in blockdiagram form in order to avoid obscuring the concepts of the describedembodiments.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope and spirit of the disclosure and appended claims. For example,due to the nature of software, functions described above can beimplemented using software executed by a processor, hardware, firmware,hardwiring, or combinations of any of these. Features implementingfunctions may also be physically located at various positions, includingbeing distributed such that portions of functions are implemented atdifferent physical locations. Also, as used herein, including in theclaims, “or” as used in a list of items prefaced by “at least one of”indicates a disjunctive list such that, for example, a list of “at leastone of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., Aand B and C).

Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage medium may be anyavailable medium that can be accessed by a general purpose or specialpurpose computer. By way of example, and not limitation,computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code means in the form of instructions or data structures andthat can be accessed by a general-purpose or special-purpose computer,or a general-purpose or special-purpose processor. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The previous description of the disclosure is provided to enable aperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Throughout this disclosure the term “example” or“exemplary” indicates an example or instance and does not imply orrequire any preference for the noted example. Thus, the disclosure isnot to be limited to the examples and designs described herein but is tobe accorded the widest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method for facilitating Machine TypeCommunication (MTC) in a wireless communications system, the methodcomprising: receiving an MTC-specific system information block at an MTCdevice, wherein the MTC-specific system information block comprisesfirst system information included in a first system information blockand second system information included in a second system informationblock; and processing the MTC-specific system information block at theMTC device.
 2. The method of claim 1, wherein the first systeminformation block and the second system information block are eachselected from a group that consists of: system information block 1(SIB1), system information block 2 (SIB2), and system information block12 (SIB12).
 3. The method of claim 1, wherein the MTC-specific systeminformation block consists of: a subset of system information includedin the first system information block or the second system informationblock.
 4. The method of claim 3, wherein the subset of systeminformation included in the first system information block or the secondsystem information block comprises: system information block 1 (SIB1),system information block 2 (SIB2), or system information block 12(SIB12).
 5. The method of claim 1, wherein the MTC-specific systeminformation block comprises fields for: cell access information,scheduling information for other system information blocks, and radioresource configuration information.
 6. The method of claim 1, whereinthe MTC-specific system information block comprises: fields for cellaccess information and cell selection information; or fields forscheduling information for other system information blocks.
 7. Themethod of claim 1, wherein the MTC-specific system information blockcomprises fields for: MTC random access channel (RACH) configurationinformation or MTC paging channel configuration information.
 8. Themethod of claim 1, wherein the MTC-specific system information blockconsists of fields for: physical uplink shared channel (PUSCH)configuration information, power control, and a timer.
 9. The method ofclaim 1, wherein the MTC-specific system information block comprises:fields for radio resource configuration information other than physicaluplink control channel (PUSCH) configuration information and soundingreference signal (SRS) configuration information.
 10. The method ofclaim 1, wherein the MTC-specific system information block is located atone or more predetermined locations.
 11. The method of claim 10, whereinthe one or more predetermined locations are a function of a cell ID, acyclic prefix length, and a division duplex configuration.
 12. Themethod of claim 1, further comprising: receiving information regardingone or more locations of the MTC-specific system information block overan MTC physical broadcast channel.
 13. The method of claim 1, furthercomprising: determining a sleep time of the MTC device exceeds a timeduration; and reading the MTC-specific system information block when thedetermined sleep time exceeds the time duration.
 14. An apparatus forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system, the apparatus comprising: means for receiving anMTC-specific system information block at the apparatus, wherein theMTC-specific system information block comprises first system informationincluded in a first system information block and second systeminformation included in a second system information block; and means forprocessing the MTC-specific system information block at the apparatus.15. The apparatus of claim 14, wherein the MTC-specific systeminformation block consists of: a subset of system information includedin the first system information block or the second system informationblock.
 16. The apparatus of claim 14, further comprising: means forreceiving information regarding one or more locations of theMTC-specific system information block over an MTC physical broadcastchannel.
 17. The apparatus of claim 14, further comprising: means fordetermining a sleep time of the apparatus exceeds a time duration; andmeans for reading the MTC-specific system information block when thedetermined sleep time exceeds the time duration.
 18. An apparatus forfacilitating Machine Type Communication (MTC) in a wirelesscommunications system, the apparatus comprising: a processor; memory inelectronic communication with the processor; and instructions stored inthe memory, the instructions being executable by the processor to causethe apparatus to: receive an MTC-specific system information block atthe apparatus, wherein the MTC-specific system information blockcomprises first system information included in a first systeminformation block and second system information included in a secondsystem information block; and process the MTC-specific systeminformation block.
 19. The apparatus of claim 18, wherein theMTC-specific system information block consists of: a subset of systeminformation included in the first system information block or the secondsystem information block.
 20. The apparatus of claim 18, wherein theMTC-specific system information block is located at one or morepredetermined locations.
 21. The apparatus of claim 18, wherein theinstructions are executable by the processor to cause the apparatus to:receive information regarding one or more locations of the MTC-specificsystem information block over an MTC physical broadcast channel.
 22. Theapparatus of claim 18, wherein the instructions are executable by theprocessor to cause the apparatus to: determine a sleep time of theapparatus exceeds a time duration; and read the MTC-specific systeminformation block when the determined sleep time exceeds the timeduration.
 23. A non-transitory computer-readable medium store code forMachine Type Communication (MTC) in a wireless communications system,the comprising instructions executable to: receive an MTC-specificsystem information block at an MTC device, wherein the MTC-specificsystem information block comprises first system information included ina first system information block and second system information includedin a second system information block; and process the MTC-specificsystem information block at the MTC device.
 24. The non-transitorycomputer-readable medium of claim 23, wherein the MTC-specific systeminformation block consists of: a subset of system information includedin the first system information block or the second system informationblock.
 25. The non-transitory computer-readable medium of claim 23,wherein the instructions are executable to: receive informationregarding one or more locations of the MTC-specific system informationblock over an MTC physical broadcast channel.
 26. The non-transitorycomputer-readable medium of claim 23, wherein the instructions areexecutable to: determine a sleep time of the MTC device exceeds a timeduration; and read the MTC-specific system information block when thedetermined sleep time exceeds the time duration.